> For the complete documentation index, see [llms.txt](https://docs.hub88.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.hub88.io/developer-docs/hub88-apis/fundamentals.md).

# Fundamentals

Hub88 offers two key APIs: **Supplier API** and **Operator API**.

* [**Supplier API**](/developer-docs/supplier-api-reference/supplier-api-overview.md): The API is designed for **game developers and distributors**, allowing to seamlessly connect to the Hub88 platform. By using the Supplier API, you can easily provide gaming content to Hub88 partner operators, simplifying the process of reaching a broad audience without additional integrations.

{% hint style="info" %}

#### ⚡ Hand this to your AI agent for Supplier API Integration

One prompt covering every endpoint you host and every call you make, the request signing scheme, the `RS_*` statuses, and the rollback-on-bet / retry-on-win rules. Paste it into your AI tool with your stack appended and it scaffolds a working integration.

{% file src="/files/wKSzRtb7jdjkpHUDH4gs" %}

{% endhint %}

* [**Operator API**:](/developer-docs/operator-api-reference/operator-api-overview.md) The API enables iGaming providers to access an extensive range of game content. It facilitates offering an online casino experience, requiring only a single integration with Hub88 to connect with an array of game options.

{% hint style="success" %}

#### ⚡ Hand this to your AI agent for Opertor API Integration

One prompt covering the five Wallet API endpoints you implement, every Operator API call, the request signing scheme, the `RS_*` statuses, and the idempotency rules. Paste it into your AI tool with your stack appended and it scaffolds a working integration.

{% file src="/files/QnPklec13S6oUAzcJLpT" %}

{% endhint %}

<table data-card-size="large" data-column-title-hidden data-view="cards"><thead><tr><th align="center"></th><th data-hidden></th><th data-hidden></th><th data-hidden data-card-target data-type="content-ref"></th><th data-hidden data-card-cover data-type="image">Cover image</th></tr></thead><tbody><tr><td align="center">Supplier API</td><td></td><td></td><td><a href="/developer-docs/supplier-api-reference/supplier-api-overview.md">Supplier API Overview</a></td><td><a href="https://1089485291-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FF8iFPgdqAwxIxP5oQMvU%2Fuploads%2FSOY7Rm7QYKYuANJ8XOtF%2FFrame%20(13).png?alt=media&amp;token=076246d0-7baa-44a1-8188-d1958e46e12a">Frame (13).png</a></td></tr><tr><td align="center">Operator API</td><td></td><td></td><td><a href="/developer-docs/operator-api-reference/operator-api-overview.md">Operator API Overview</a></td><td><a href="https://1089485291-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FF8iFPgdqAwxIxP5oQMvU%2Fuploads%2FWVxWUHdT80NUz6s5QKTU%2FFrame%20(15).png?alt=media&amp;token=d4235834-3c5e-427b-b116-326141cf9f68">Frame (15).png</a></td></tr></tbody></table>


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://docs.hub88.io/developer-docs/hub88-apis/fundamentals.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.
